Extended 3rd generation partnership project (3gpp) framework for live uplink streaming (flus) sink capabilities description

ABSTRACT

A method, computer program, computer system, and device is provided for determining 3rd Generation Partnership Project (3GPP) Framework for Live Uplink Streaming (FLUS) sink capabilities. The method may include obtaining, by a FLUS source, a sink resource associated with a FLUS sink, wherein the sink resource indicates a direct address at which a capability described in the sink resource can be directly accessed; and accessing the capability directly by the FLUS source using the direct address.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims priority based on U.S. Provisional Application No. 63/105,077, filed Oct. 23, 2020, in the United States Patent &Trademark Office, the entirety of which is incorporated herein.

FIELD

This disclosure relates generally to field of data processing, and more particularly to media processing.

BACKGROUND

The 3rd Generation Partnership Project (3GPP) Framework for Live Uplink Streaming (FLUS) protocol provides a mechanism for uplink streaming of multimedia content from a source device to the network and sending/distributing that content to one or more destinations. The protocol has a vendor-specific capability description, and does not provide any detail description for achieving interoperability. The protocol also does not provide a specific address for reaching the capability.

SUMMARY

Embodiments relate to a method, system, and computer readable medium for accessing 3GPP FLUS sink capabilities. Provided are methods for signaling the address of a capability in the FLUS sink capabilities discovery. Describing the address of a FLUS sink capability may enable the access of that capability directly

According to one aspect, a method for accessing 3GPP FLUS sink capabilities is provided. The method may include obtaining, by a FLUS source, a sink resource associated with a FLUS sink, wherein the sink resource indicates a direct address at which a capability described in the sink resource can be directly accessed; and accessing the capability directly by the FLUS source using the direct address.

According to another aspect, a device for accessing 3GPP FLUS sink capabilities is provided. The device may include at least one memory configured to store program code; and at least one processor configured to read the program code and operate as instructed by the program code, the program code including: obtaining code configured to cause the at least one processor to obtain, by a FLUS source, a sink resource associated with a FLUS sink, wherein the sink resource indicates a direct address at which a capability described in the sink resource can be directly accessed; and accessing code configured to cause the at least one processor to access the capability directly by the FLUS source using the direct address.

According to yet another aspect, a computer readable medium for accessing 3GPP FLUS sink capabilities is provided. The computer readable medium may have stored thereon computer program for accessing 3GPP FLUS sink capabilities, and the computer program may be configured to cause one or more computer processors to: obtain, by a FLUS source, a sink resource associated with a FLUS sink, wherein the sink resource indicates a direct address at which a capability described in the sink resource can be directly accessed; and access the capability directly by the FLUS source using the direct address.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other objects, features and advantages will become apparent from the following detailed description of illustrative embodiments, which is to be read in connection with the accompanying drawings. The various features of the drawings are not to scale as the illustrations are for clarity in facilitating the understanding of one skilled in the art in conjunction with the detailed description. In the drawings:

FIG. 1 illustrates a networked computer environment according to at least one embodiment;

FIG. 2 is a block diagram of a system for determining 3GPP FLUS sink capabilities, according to at least one embodiment;

FIG. 3 is an operational flowchart illustrating the steps carried out by a program for accessing 3GPP FLUS sink capabilities, according to at least one embodiment;

FIG. 4 is a block diagram of internal and external components of computers and servers depicted in FIG. 1 according to at least one embodiment;

FIG. 5 is a block diagram of an illustrative cloud computing environment including the computer system depicted in FIG. 1, according to at least one embodiment; and

FIG. 6 is a block diagram of functional layers of the illustrative cloud computing environment of FIG. 5, according to at least one embodiment.

DETAILED DESCRIPTION

Detailed embodiments of the claimed structures and methods are disclosed herein; however, it can be understood that the disclosed embodiments are merely illustrative of the claimed structures and methods that may be embodied in various forms. Those structures and methods may, however, be embodied in many different forms and should not be construed as limited to the exemplary embodiments set forth herein. Rather, these exemplary embodiments are provided so that this disclosure will be thorough and complete and will fully convey the scope to those skilled in the art. In the description, details of well-known features and techniques may be omitted to avoid unnecessarily obscuring the presented embodiments.

As previously described, The 3rd Generation Partnership Project (3GPP) Framework for Live Uplink Streaming (FLUS) protocol provides a mechanism for uplink streaming of multimedia content from a source device to the network and sending/distributing that content to one or more destinations. The protocol has a vendor-specific capability description. In the 3GPP FLUS protocol, the source device of media streams establishes an uplink session with a Sink through the network. The FLUS APIs allows the source device to control the session and also the Sink to provide feedback or remote control of the source device. The 3GPP FLUS protocol supports retrieving the sink capabilities by the FLUS source. However, the capabilities are documented a list of vendor-specific URNs. If the FLUS source does not recognize a URN, the FLUS source may not know the corresponding capabilities, and interoperability may only be achieved at the vendor level, not across vendors. It may be advantageous, therefore, to define a method for the description of the FLUS sink capabilities in order to enable the FLUS source and application on the device or network to use the capabilities and run services on the sink device or a cloud platform.

Aspects are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer readable media according to the various embodiments. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions.

The following described exemplary embodiments provide a system, method and computer program that allows for determining 3GPP FLUS sink capabilities. Referring now to FIG. 1, a functional block diagram of a networked computer environment illustrating a media processing system 100 (hereinafter “system”) for determining 3GPP FLUS sink capabilities. It should be appreciated that FIG. 1 provides only an illustration of one implementation and does not imply any limitations with regard to the environments in which different embodiments may be implemented. Many modifications to the depicted environments may be made based on design and implementation requirements.

The system 100 may include a computer 102 and a server computer 114. The computer 102 may communicate with the server computer 114 via a communication network 110 (hereinafter “network”). The computer 102 may include a processor 104 and a software program 108 that is stored on a data storage device 106 and is enabled to interface with a user and communicate with the server computer 114. As will be discussed below with reference to FIG. 4 the computer 102 may include internal components 800A and external components 900A, respectively, and the server computer 114 may include internal components 800B and external components 900B, respectively. The computer 102 may be, for example, a mobile device, a telephone, a personal digital assistant, a netbook, a laptop computer, a tablet computer, a desktop computer, or any type of computing devices capable of running a program, accessing a network, and accessing a database.

The server computer 114 may also operate in a cloud computing service model, such as Software as a Service (SaaS), Platform as a Service (PaaS), or Infrastructure as a Service (laaS), as discussed below with respect to FIGS. 5 and 6. The server computer 114 may also be located in a cloud computing deployment model, such as a private cloud, community cloud, public cloud, or hybrid cloud.

The server computer 114, which may be used for determining 3GPP FLUS sink capabilities is enabled to run an 3GPP FLUS Capabilities Accessing Program 116 (hereinafter “program”) that may interact with a database 112. The 3GPP FLUS Capabilities Accessing Program method is explained in more detail below Accessing with respect to FIG. 3. In one embodiment, the computer 102 may operate as an input device including a user interface while the program 116 may run primarily on server computer 114. In an alternative embodiment, the program 116 may run primarily on one or more computers 102 while the server computer 114 may be used for processing and storage of data used by the program 116. It should be noted that the program 116 may be a standalone program or may be integrated into a larger 3GPP FLUS Capabilities Accessing program.

It should be noted, however, that processing for the program 116 may, in some instances be shared amongst the computers 102 and the server computers 114 in any ratio. In another embodiment, the program 116 may operate on more than one computer, server computer, or some combination of computers and server computers, for example, a plurality of computers 102 communicating across the network 110 with a single server computer 114. In another embodiment, for example, the program 116 may operate on a plurality of server computers 114 communicating across the network 110 with a plurality of client computers. Alternatively, the program may operate on a network server communicating across the network with a server and a plurality of client computers.

The network 110 may include wired connections, wireless connections, fiber optic connections, or some combination thereof. In general, the network 110 can be any combination of connections and protocols that will support communications between the computer 102 and the server computer 114. The network 110 may include various types of networks, such as, for example, a local area network (LAN), a wide area network (WAN) such as the Internet, a telecommunication network such as the Public Switched Telephone Network (PSTN), a wireless network, a public switched network, a satellite network, a cellular network (e.g., a fifth generation (5G) network, a long-term evolution (LTE) network, a third generation (3G) network, a code division multiple access (CDMA) network, etc.), a public land mobile network (PLMN), a metropolitan area network (MAN), a private network, an ad hoc network, an intranet, a fiber optic-based network, or the like, and/or a combination of these or other types of networks.

The number and arrangement of devices and networks shown in FIG. 1 are provided as an example. In practice, there may be additional devices and/or networks, fewer devices and/or networks, different devices and/or networks, or differently arranged devices and/or networks than those shown in FIG. 1. Furthermore, two or more devices shown in FIG. 1 may be implemented within a single device, or a single device shown in FIG. 1 may be implemented as multiple, distributed devices. Additionally, or alternatively, a set of devices (e.g., one or more devices) of system 100 may perform one or more functions described as being performed by another set of devices of system 100.

Referring now to FIG. 2, a block diagram of a 3GPP FLUS architecture 200 is depicted. The 3GPP FLUS architecture 200 may include a first user environment 202 and a second user environment 204. The first user environment 202 may include one or more capture devices 206 and a FLUS source 208. The FLUS source 208 may include a control source 210, a media source 212, an assistance receiver 214, and a remote control target 216. The second user environment 204 may include a FLUS sink 218, an assistance sender 220, and a remote controller 222. The FLUS sink 218 may include a control sink 224 and a media sink 226.

Embodiments may relate to a method for signaling the address of a capabilities in the FLUS sink capabilities discovery. Describing the address of a FLUS sink capability may enable the access of that capability directly.

In the current 3GPP FLUS protocol, the source device of media streams establishes an uplink session with a Sink through the network. The FLUS APIs allows the source device to control the session and also the Sink to provide feedback or remote control of the source device.

The current 3GPP FLUS protocol supports retrieving the sink capabilities by the FLUS source as well as a possible description. However, it doesn't provide an address to reach that capability directly. For some applications, a direct access to a capability is required.

An example of a sink resource corresponding to a FLUS sink, for example FLUS sink 218, is set forth in Table 1, below:

TABLE 1 Properties of Sink Resource Property Name Description Example Values capabilities List of supported features and { “scheme” : instantiations by the FLUS sink. urn:vnd:xzy:capability-name, Each capability is to be expressed “location” : using an object element of an “http://vnd.com/xzy/capability- array. The object has the following name” attributes: } A scheme URN to identify the capability An optional location URL, from which a description for the capability can be retrieved. The format of description is defined by the scheme URN.

A FLUS source, for example FLUS source 208, can retrieve the resource description of a sink resource and find out its capabilities based on the entries of Table 1. But the address of the capability is not provided.

In embodiments, the address of a capability may be added to the above table according to one or more of the Examples below:

Example 1: A structure may be defined for the resource at the address defined by the location URL which include an address field:

{  “url”: “URL-address”,  ...  }

In Example 1, the location item shall have an “url” item which includes the URL of the capability.

Example 2: The capabilities array element may have an additional “url” item:

{ “scheme”: “urn:vnd:xzy:capability-name”,  “location”: “http://vnd.com/xzy/capability-name”,  “url”: “URL-address” }

In Example 2, the “url” item may include the URL address of the capability.

Table 2A and Table 2B demonstrate examples of the capability object in JSON format. In embodiments, Table 2A may correspond to Example 1 above, and Table 2B may correspond to Example 2 above.

TABLE 2A {  ″uri″: ″ urn:vnd:xzy:capability-name″,  ″location″: ″http://vnd.com/xzy/capability-name″, } Resource at http://vnd.com/xzy/capability-name: {  ″url″: ″http://vnd.com/xzy/capability-url″,  .... }

TABLE 2B {  ″uri″: ″ urn:vnd:xzy:capability-name″,  ″location″: ″http://ynd.com/xzy/capability-name″,  ″url″: ″http://vnd.com/xzy/capability-url″,  } }

Accordingly, embodiments may relate to a method for describing the location of a 3GPP FLUS sink capability wherein the address of the capability is signaled in the sink capabilities resource, and therefore that capability can be accessed directly using the address, wherein the address can be either included in the description resource or it can be added as a new item to the Sink capabilities resource.

FIG. 4 is a flowchart illustrating example process 400 for accessing 3GPP FLUS sink capabilities. FIG. 3 may be described with the aid of FIGS. 1 and 2. As previously described, the 3GPP FLUS Capabilities Accessing Program 116 (FIG. 1) may allow for a FLUS source and application on a device or network to use the capabilities and run services on the sink device or a cloud platform.

As shown in FIG. 3, process 300 may include obtaining, by a FLUS source, a sink resource associated with a FLUS sink, wherein the sink resource indicates a direct address at which a capability described in the sink resource can be directly accessed (block 310).

As further shown in FIG. 3, process 300 may include accessing the capability directly by the FLUS source using the direct address (block 320).

In embodiments, the sink resource may indicate a capability description location from which a capability description can be retrieved, and the direct address may be included in the capability description.

In embodiments, the capability description location may be indicated by a first uniform resource locator included in the sink resource, and the direct address may be indicated by a second uniform resource locator included in the capability description.

In embodiments, the capability may be described in the sink resource using an element of an array.

In embodiments, the direct address may be included in the element of the array.

In embodiments, the direct address may be indicated by a uniform resource locator included in the element of the array.

In embodiments, the element of the array may further include a uniform resource name indicating the capability.

It may be appreciated that FIG. 3 provides only an illustration of one implementation and does not imply any limitations with regard to how different embodiments may be implemented. Many modifications to the depicted environments may be made based on design and implementation requirements.

FIG. 4 is a block diagram 400 of internal and external components of computers depicted in FIG. 1 in accordance with an illustrative embodiment. It should be appreciated that FIG. 4 provides only an illustration of one implementation and does not imply any limitations with regard to the environments in which different embodiments may be implemented. Many modifications to the depicted environments may be made based on design and implementation requirements.

Computer 102 (FIG. 1) and server computer 114 (FIG. 1) may include respective sets of internal components 800A,B and external components 900A,B illustrated in FIG. 4. Each of the sets of internal components 800 include one or more processors 820, one or more computer-readable RAMs 822 and one or more computer-readable ROMs 824 on one or more buses 826, one or more operating systems 828, and one or more computer-readable tangible storage devices 830.

Processor 820 is implemented in hardware, firmware, or a combination of hardware and software. Processor 820 is a central processing unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), a microprocessor, a microcontroller, a digital signal processor (DSP), a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), or another type of processing component. In some implementations, processor 820 includes one or more processors capable of being programmed to perform a function. Bus 826 includes a component that permits communication among the internal components 800A,B.

The one or more operating systems 828, the software program 108 (FIG. 1) and the 3GPP FLUS Capabilities Accessing Program 116 (FIG. 1) on server computer 114 (FIG. 1) are stored on one or more of the respective computer-readable tangible storage devices 830 for execution by one or more of the respective processors 820 via one or more of the respective RAMs 822 (which typically include cache memory). In the embodiment illustrated in FIG. 4, each of the computer-readable tangible storage devices 830 is a magnetic disk storage device of an internal hard drive. Alternatively, each of the computer-readable tangible storage devices 830 is a semiconductor storage device such as ROM 824, EPROM, flash memory, an optical disk, a magneto-optic disk, a solid state disk, a compact disc (CD), a digital versatile disc (DVD), a floppy disk, a cartridge, a magnetic tape, and/or another type of non-transitory computer-readable tangible storage device that can store a computer program and digital information.

Each set of internal components 800A,B also includes a R/W drive or interface 832 to read from and write to one or more portable computer-readable tangible storage devices 936 such as a CD-ROM, DVD, memory stick, magnetic tape, magnetic disk, optical disk or semiconductor storage device. A software program, such as the software program 108 (FIG. 1) and the 3GPP FLUS Capabilities Accessing Program 116 (FIG. 1) can be stored on one or more of the respective portable computer-readable tangible storage devices 936, read via the respective R/W drive or interface 832 and loaded into the respective hard drive 830.

Each set of internal components 800A,B also includes network adapters or interfaces 836 such as a TCP/IP adapter cards; wireless Wi-Fi interface cards; or 3G, 4G, or 5G wireless interface cards or other wired or wireless communication links. The software program 108 (FIG. 1) and the 3GPP FLUS Capabilities Accessing Program 116 (FIG. 1) on the server computer 114 (FIG. 1) can be downloaded to the computer 102 (FIG. 1) and server computer 114 from an external computer via a network (for example, the Internet, a local area network or other, wide area network) and respective network adapters or interfaces 836. From the network adapters or interfaces 836, the software program 108 and the 3GPP FLUS Capabilities Accessing Program 116 on the server computer 114 are loaded into the respective hard drive 830. The network may comprise copper wires, optical fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers.

Each of the sets of external components 900A,B can include a computer display monitor 920, a keyboard 930, and a computer mouse 934. External components 900A,B can also include touch screens, virtual keyboards, touch pads, pointing devices, and other human interface devices. Each of the sets of internal components 800A,B also includes device drivers 840 to interface to computer display monitor 920, keyboard 930 and computer mouse 934. The device drivers 840, R/W drive or interface 832 and network adapter or interface 836 comprise hardware and software (stored in storage device 830 and/or ROM 824).

It is understood in advance that although this disclosure includes a detailed description on cloud computing, implementation of the teachings recited herein are not limited to a cloud computing environment. Rather, some embodiments are capable of being implemented in conjunction with any other type of computing environment now known or later developed.

Cloud computing is a model of service delivery for enabling convenient, on-demand network access to a shared pool of configurable computing resources (e.g. networks, network bandwidth, servers, processing, memory, storage, applications, virtual machines, and services) that can be rapidly provisioned and released with minimal management effort or interaction with a provider of the service. This cloud model may include at least five characteristics, at least three service models, and at least four deployment models.

Characteristics are as follows:

On-demand self-service: a cloud consumer can unilaterally provision computing capabilities, such as server time and network storage, as needed automatically without requiring human interaction with the service's provider.

Broad network access: capabilities are available over a network and accessed through standard mechanisms that promote use by heterogeneous thin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

Resource pooling: the provider's computing resources are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned according to demand. There is a sense of location independence in that the consumer generally has no control or knowledge over the exact location of the provided resources but may be able to specify location at a higher level of abstraction (e.g., country, state, or datacenter).

Rapid elasticity: capabilities can be rapidly and elastically provisioned, in some cases automatically, to quickly scale out and rapidly released to quickly scale in. To the consumer, the capabilities available for provisioning often appear to be unlimited and can be purchased in any quantity at any time.

Measured service: cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported providing transparency for both the provider and consumer of the utilized service.

Service Models are as follows:

Software as a Service (SaaS): the capability provided to the consumer is to use the provider's applications running on a cloud infrastructure. The applications are accessible from various client devices through a thin client interface such as a web browser (e.g., web-based e-mail). The consumer does not manage or control the underlying cloud infrastructure including network, servers, operating systems, storage, or even individual application capabilities, with the possible exception of limited user-specific application configuration settings.

Platform as a Service (PaaS): the capability provided to the consumer is to deploy onto the cloud infrastructure consumer-created or acquired applications created using programming languages and tools supported by the provider. The consumer does not manage or control the underlying cloud infrastructure including networks, servers, operating systems, or storage, but has control over the deployed applications and possibly application hosting environment configurations.

Infrastructure as a Service (laaS): the capability provided to the consumer is to provision processing, storage, networks, and other fundamental computing resources where the consumer is able to deploy and run arbitrary software, which can include operating systems and applications. The consumer does not manage or control the underlying cloud infrastructure but has control over operating systems, storage, deployed applications, and possibly limited control of select networking components (e.g., host firewalls).

Deployment Models are as follows:

Private cloud: the cloud infrastructure is operated solely for an organization. It may be managed by the organization or a third party and may exist on-premises or off-premises.

Community cloud: the cloud infrastructure is shared by several organizations and supports a specific community that has shared concerns (e.g., mission, security requirements, policy, and compliance considerations). It may be managed by the organizations or a third party and may exist on-premises or off-premises.

Public cloud: the cloud infrastructure is made available to the general public or a large industry group and is owned by an organization selling cloud services.

Hybrid cloud: the cloud infrastructure is a composition of two or more clouds (private, community, or public) that remain unique entities but are bound together by standardized or proprietary technology that enables data and application portability (e.g., cloud bursting for load-balancing between clouds).

A cloud computing environment is service oriented with a focus on statelessness, low coupling, modularity, and semantic interoperability. At the heart of cloud computing is an infrastructure comprising a network of interconnected nodes.

Referring to FIG. 5, illustrative cloud computing environment 500 is depicted. As shown, cloud computing environment 500 comprises one or more cloud computing nodes 10 with which local computing devices used by cloud consumers, such as, for example, personal digital assistant (PDA) or cellular telephone 54A, desktop computer 54B, laptop computer 54C, and/or automobile computer system 54N may communicate. Cloud computing nodes 10 may communicate with one another. They may be grouped (not shown) physically or virtually, in one or more networks, such as Private, Community, Public, or Hybrid clouds as described hereinabove, or a combination thereof. This allows cloud computing environment 500 to offer infrastructure, platforms and/or software as services for which a cloud consumer does not need to maintain resources on a local computing device. It is understood that the types of computing devices 54A-N shown in FIG. 5 are intended to be illustrative only and that cloud computing nodes 10 and cloud computing environment 500 can communicate with any type of computerized device over any type of network and/or network addressable connection (e.g., using a web browser).

Referring to FIG. 6, a set of functional abstraction layers 600 provided by cloud computing environment 500 (FIG. 5) is shown. It should be understood in advance that the components, layers, and functions shown in FIG. 6 are intended to be illustrative only and embodiments are not limited thereto. As depicted, the following layers and corresponding functions are provided:

Hardware and software layer 60 includes hardware and software components.

Examples of hardware components include: mainframes 61; RISC (Reduced Instruction Set Computer) architecture based servers 62; servers 63; blade servers 64; storage devices 65; and networks and networking components 66. In some embodiments, software components include network application server software 67 and database software 68.

Virtualization layer 70 provides an abstraction layer from which the following examples of virtual entities may be provided: virtual servers 71; virtual storage 72; virtual networks 73, including virtual private networks; virtual applications and operating systems 74; and virtual clients 75.

In one example, management layer 80 may provide the functions described below.

Resource provisioning 81 provides dynamic procurement of computing resources and other resources that are utilized to perform tasks within the cloud computing environment. Metering and Pricing 82 provide cost tracking as resources are utilized within the cloud computing environment, and billing or invoicing for consumption of these resources. In one example, these resources may comprise application software licenses. Security provides identity verification for cloud consumers and tasks, as well as protection for data and other resources. User portal 83 provides access to the cloud computing environment for consumers and system administrators. Service level management 84 provides cloud computing resource allocation and management such that required service levels are met. Service Level Agreement (SLA) planning and fulfillment 85 provide pre-arrangement for, and procurement of, cloud computing resources for which a future requirement is anticipated in accordance with an SLA.

Workloads layer 90 provides examples of functionality for which the cloud computing environment may be utilized. Examples of workloads and functions which may be provided from this layer include: mapping and navigation 91; software development and lifecycle management 92; virtual classroom education delivery 93; data analytics processing 94; transaction processing 95; and 3GPP FLUS Capabilities Determination 96. 3GPP FLUS Capabilities Determination 96 may allow for enabling the FLUS source and application on a device or network to use the capabilities and run services on the sink device or a cloud platform.

Some embodiments may relate to a system, a method, and/or a computer readable medium at any possible technical detail level of integration. The computer readable medium may include a computer-readable non-transitory storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out operations.

The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.

Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.

Computer readable program code/instructions for carrying out operations may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, configuration data for integrated circuitry, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++, or the like, and procedural programming languages, such as the “C” programming language or similar programming languages. The computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects or operations.

These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.

The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer readable media according to various embodiments. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). The method, computer system, device, and computer readable medium may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in the Figures. In some alternative implementations, the functions noted in the blocks may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed concurrently or substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.

It will be apparent that systems and/or methods, described herein, may be implemented in different forms of hardware, firmware, or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and/or methods is not limiting of the implementations. Thus, the operation and behavior of the systems and/or methods were described herein without reference to specific software code—it being understood that software and hardware may be designed to implement the systems and/or methods based on the description herein.

No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items, and may be used interchangeably with “one or more.” Furthermore, as used herein, the term “set” is intended to include one or more items (e.g., related items, unrelated items, a combination of related and unrelated items, etc.), and may be used interchangeably with “one or more.” Where only one item is intended, the term “one” or similar language is used. Also, as used herein, the terms “has,” “have,” “having,” or the like are intended to be open-ended terms. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise.

The descriptions of the various aspects and embodiments have been presented for purposes of illustration, but are not intended to be exhaustive or limited to the embodiments disclosed. Even though combinations of features are recited in the claims and/or disclosed in the specification, these combinations are not intended to limit the disclosure of possible implementations. In fact, many of these features may be combined in ways not specifically recited in the claims and/or disclosed in the specification. Although each dependent claim listed below may directly depend on only one claim, the disclosure of possible implementations includes each dependent claim in combination with every other claim in the claim set. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope of the described embodiments. The terminology used herein was chosen to best explain the principles of the embodiments, the practical application or technical improvement over technologies found in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein. 

What is claimed is:
 1. A method for accessing 3rd Generation Partnership Project (3GPP) Framework for Live Uplink Streaming (FLUS) sink capabilities, executable by a processor, comprising: obtaining, by a FLUS source, a sink resource associated with a FLUS sink, wherein the sink resource indicates a direct address at which a capability described in the sink resource can be directly accessed; and accessing the capability directly by the FLUS source using the direct address.
 2. The method of claim 1, wherein the sink resource indicates a capability description location from which a capability description can be retrieved, and wherein the direct address is included in the capability description.
 3. The method of claim 2, wherein the capability description location is indicated by a first uniform resource locator included in the sink resource, and wherein the direct address is indicated by a second uniform resource locator included in the capability description.
 4. The method of claim 1, wherein the capability is described in the sink resource using an element of an array.
 5. The method of claim 4, wherein the direct address is included in the element of the array.
 6. The method of claim 5, wherein the direct address is indicated by a uniform resource locator included in the element of the array.
 7. The method of claim 6, wherein the element of the array further comprises a uniform resource name indicating the capability.
 8. A device for accessing 3rd Generation Partnership Project (3GPP) Framework for Live Uplink Streaming (FLUS) sink capabilities, the device comprising: at least one memory configured to store program code; and at least one processor configured to read the program code and operate as instructed by the program code, the program code including: obtaining code configured to cause the at least one processor to obtain, by a FLUS source, a sink resource associated with a FLUS sink, wherein the sink resource indicates a direct address at which a capability described in the sink resource can be directly accessed; and accessing code configured to cause the at least one processor to access the capability directly by the FLUS source using the direct address.
 9. The device of claim 8, wherein the sink resource indicates a capability description location from which a capability description can be retrieved, and wherein the direct address is included in the capability description.
 10. The device of claim 9, wherein the capability description location is indicated by a first uniform resource locator included in the sink resource, and wherein the direct address is indicated by a second uniform resource locator included in the capability description.
 11. The device of claim 10, wherein the capability is described in the sink resource using an element of an array.
 12. The device of claim 11, wherein the direct address is included in the element of the array.
 13. The device of claim 12, wherein the direct address is indicated by a uniform resource locator included in the element of the array.
 14. The device of claim 13, wherein the element of the array further comprises a uniform resource name indicating the capability.
 15. A non-transitory computer readable medium having stored thereon a computer program for accessing 3rd Generation Partnership Project (3GPP) Framework for Live Uplink Streaming (FLUS) sink capabilities, the computer program configured to cause one or more computer processors to: obtain, by a FLUS source, a sink resource associated with a FLUS sink, wherein the sink resource indicates a direct address at which a capability described in the sink resource can be directly accessed; and access the capability directly by the FLUS source using the direct address.
 16. The non-transitory computer readable medium of claim 15, wherein the sink resource indicates a capability description location from which a capability description can be retrieved, and wherein the direct address is included in the capability description.
 17. The non-transitory computer readable medium of claim 16, wherein the capability description location is indicated by a first uniform resource locator included in the sink resource, and wherein the direct address is indicated by a second uniform resource locator included in the capability description.
 18. The non-transitory computer readable medium of claim 17, wherein the capability is described in the sink resource using an element of an array.
 19. The non-transitory computer readable medium of claim 18, wherein the direct address is included in the element of the array.
 20. The non-transitory computer readable medium of claim 19, wherein the direct address is indicated by a uniform resource locator included in the element of the array. 